🔧 fix(ci): restore git credentials for post-release automation#159
Merged
Conversation
gaborbernat
had a problem deploying
to
auto-merge
GitHub Actions
Failure
gaborbernat
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The zizmor security tool added
persist-credentials: falseto the checkout step, which broke the post-release workflow. After publishing to the JetBrains Marketplace, the job creates a version bump PR by pushing a new branch, but credential stripping caused authentication failures.Removing
persist-credentials: falserestores the ability to push branches for automated PRs. 🔐 Theartipackedwarning is suppressed with an inline ignore because it's a false positive—this job uploads plugin distributions to GitHub releases, not artifacts containing the.gitdirectory that could leak credentials.This change only affects the release workflow. The credentials are already protected by the
releaseenvironment requirement.